SURFACE VEHICLE RECOMMENDED PRACTICE
Application configurable Messaging
SAE Technical Standards Board Rules provide that: This report is published by SAE to advance the state of technical and engineering sciences. The use of this report is
entirely voluntary, and its applicability and suitability for any particular use, including any patent infringement arising therefrom, is the sole responsibility of the user.?
SAE reviews each technical report at least every five years at which time it may be reaffirmed, revised, or cancelled. SAE invites your written comments and suggestions.
前言：
This series of SAE Recommended Practices have been developed by the Truck and Bus Control and
Communications Network Subcommittee of the Truck and Bus Electrical and Electronics Committee.
The objectives of the subcommittee are to develop information reports, recommended practices, and
standards concerned with the requirements, design, and usage of devices that transmit electronic signals
and control information among vehicle components.
The usage of these Recommended Practices is not limited to truck and bus applications; 其他 applications may be accommodated with immediate support being provided for construction and agricultural equipment, and stationary power systems.
These SAE Recommended Practices are intended as a guide toward standard practice and are subject
to 改变 so as to keep pace with experience and technical advances.
This application layer may be used for all SAE J1939 applications. It is the characteristic that is common
across all SAE J1939 applications.
目录
1 Scope .................................................................................................................................... 4
2 References............................................................................................................................ 4
2.1 Applicable Publications .......................................................................................................... 4
2.1.1 SAE Publications................................................................................................................... 4
2.2 Related Publications .............................................................................................................. 4
2.2.1 ISO Publications.................................................................................................................... 4
3 Definitions.............................................................................................................................. 5
4 Abbreviations ......................................................................................................................... 5
5 Technical Requirements ........................................................................................................ 5
5.1 General.................................................................................................................................. 5
5.2 Overview of Configuration Services....................................................................................... 5
5.2.1 Developmental History ........................................................................................................... 5
5.2.2 Harmonization ........................................................................................................................ 6
5.2.3 Operation and Related Requirements ................................................................................... 6
5.2.3.1 Effects Upon Request Messages........................................................................................... 7
5.2.3.2 Additional CA Requirements.................................................................................................. 8
5.2.3.3 Application for New Parameter Definitions ............................................................................ 8
SAE J1939-74 Issued SEP2004
- 2 -
5.2.3.4 Continuity Across Power Cycles............................................................................................ 9
5.3 The Configuration Service ..................................................................................................... 9
5.3.1 Configuration Identification Message..................................................................................... 9
5.3.1.1 PGN of Message Being Configured..................................................................................... 10
5.3.1.2 Parameter Being Included ................................................................................................... 10
5.3.1.3 Position of Configured Parameter....................................................................................... 11
5.3.1.4 Number of Parameters Included.......................................................................................... 11
5.3.1.5 Message Will Be Used Proprietarily..................................................................................... 11
5.3.1.6 Message Will Use Transport Protocol ................................................................................. 12
5.3.1.7 First Parameter Only Being Identified .................................................................................. 13
5.3.1.8 Starting Bit for this Parameter.............................................................................................. 13
5.3.1.9 Requirements Related to Configuration Identification Message.......................................... 15
5.3.2 Parameter Locate Message................................................................................................. 16
5.3.2.1 Parameter to be Located...................................................................................................... 16
5.3.2.2 Parameter Locate Command............................................................................................... 17
5.3.3 Request for Complete Configurable Message Set .............................................................. 17
5.3.3.1 Message Selection Control .................................................................................................. 18
5.3.3.2 PGN of Configurable Message Desired............................................................................... 18
5.4 The Set of Destination Specific Proprietarily Configurable Messages ................................ 19
5.4.1 Destination Specific Proprietarily Configurable Message 1................................................. 19
5.4.1.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 19
5.4.1.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 20
5.4.2 Destination Specific Proprietarily Configurable Message 2................................................. 20
5.4.2.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 20
5.4.2.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 20
5.4.3 Destination Specific Proprietarily Configurable Message 3................................................. 21
5.4.3.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 21
5.4.3.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 21
5.4.4 Destination Specific Proprietarily Configurable Message 4................................................. 21
5.4.4.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 22
5.4.4.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 22
5.4.5 Destination Specific Proprietarily Configurable Message 5................................................. 22
5.4.5.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 23
5.4.5.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 23
5.4.6 Destination Specific Proprietarily Configurable Message 6................................................. 23
5.4.6.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 23
5.4.6.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 24
5.4.7 Destination Specific Proprietarily Configurable Message 7................................................. 24
5.4.7.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 24
5.4.7.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 24
5.4.8 Destination Specific Proprietarily Configurable Message 8................................................. 25
5.4.8.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 25
5.4.8.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 25
5.4.9 Destination Specific Proprietarily Configurable Message 9................................................. 25
5.4.9.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 26
5.4.9.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 26
5.4.10 Destination Specific Proprietarily Configurable Message 10............................................... 26
5.4.10.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 26
5.4.10.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 27
SAE J1939-74 Issued SEP2004
- 3 -
5.4.11 Destination Specific Proprietarily Configurable Message 11............................................... 27
5.4.11.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 27
5.4.11.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 27
5.4.12 Destination Specific Proprietarily Configurable Message 12............................................... 28
5.4.12.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 28
5.4.12.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 28
5.4.13 Destination Specific Proprietarily Configurable Message 1................................................. 28
5.4.13.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 29
5.4.13.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 29
5.4.14 Destination Specific Proprietarily Configurable Message 14............................................... 29
5.4.14.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 29
5.4.14.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 30
5.4.15 Destination Specific Proprietarily Configurable Message 15............................................... 30
5.4.15.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 30
5.4.15.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 30
5.4.16 Destination Specific Proprietarily Configurable Message 16............................................... 31
5.4.16.1 Parameter Content of Destination Specific Proprietarily Configurable Messages .............. 31
5.4.16.2 DLC for Destination Specific Proprietarily Configurable Messages .................................... 31
5.5 The Set of Parameters for Use within the Configurable Messages..................................... 31
6 Notes ................................................................................................................................... 32
6.1 Marginal Indicia .................................................................................................................... 32
Appendix A ASSUMPTIONS USED TO DESIGN CONFIGURABLE MESSAGING .............................. 33
Appendix B APPLICATION RULES REGARDING CONFIGURABLE MESSAGING............................. 35
Appendix C PARAMETERS FOR CONFIGURABLE MESSAGING ....................................................... 36
LIST OF FIGURES
There are no Figures contained in this document
LIST OF TABLES
There are no Tables contained in this document
SAE J1939-74 Issued SEP2004
- 4 -
1. Scope
The SAE J1939 documents are intended for light, medium, and heavy-duty vehicles used on or off road
as well as appropriate stationary applications which use vehicle derived components (e.g. generator
sets). Vehicles of interest include, but are not limited to, on- and off-highway trucks and their trailers,
construction equipment, and agricultural equipment and implements.
The purpose of these documents is to provide an open inter连接 system for electronic systems. It is
the intention of these documents to allow Electronic Control Units to communicate with each 其他 by
providing a standard architecture.
This particular document, SAE J1939-74, describes the message structure for a set of messages which
enable the user to determine and announce to 其他s on the network, the parameter placement within a
particular message from the special set of messages defined within this document.
2. References
2.1 Applicable Publications
General information regarding this series of recommended practices is found in SAE J1939. The latest
issue of SAE publications shall apply.
2.1.1 SAE PUBLICATIONS
Available from SAE, 400 Commonwealth Drive, Warrendale, PA 15096-0001.
SAE J1939RPractice for a Serial Control and Communications Vehicle Network is the
parent document and should be referenced in general.
SAE J1939-21桪ata Link Layer
SAE J1939-71梀ehicle Application Layer
SAE J1939-73桝pplication Layer - Diagnostics
SAE J1939-81桸etwork Management
2.2 Related Publications
The following publications are provided for information purposes only and are not a required part of this
document.
2.2.1 ISO PUBLICATIONS
Available from ANSI, 25 West 43rd Street, New York, NY 10036-8002.
ISO 11783桾ractors, machinery for agriculture and forestry Serial control and communications data
network
SAE J1939-74 Issued SEP2004
- 5 -
3. Definitions
Terms and definitions are defined in SAE J1939.
4. Abbreviations
CA Controller Application ?the function of a system receiving a NAME within an ecu ?see SAE
J1939?1, Network Management, for more details
SPN Suspect Parameter Number
See SAE J1939 for any terms and or definitions not found in this document.
5. Technical Requirements
This configurable messaging application provides for the variable packing of certain parameters within a
particular message from a set of messages.
5.1 General
The definitions provided herein are intended to satisfy the needs of all potential users of the SAE J1939
network. These definitions are intended to be suitable for applications in any of the industry groups
defined within SAE J1939.
The capabilities provided allow CAs to configure and identify to 其他 network
CAs the location of certain parameters (each identified by its SPN) within certain special messages (each
identified by PGN). These capabilities also provide the means by which a CA can request the
identification of the message (PGN) containing a certain parameter (SPN). This document will define the
configuration process, a set of messages which can and may be configured, and the messages used to
identify this configuration to the rest of a network. This document will also contain the definitions of the
only set of parameters (identified by SPN) to be used exclusively within one of the configured messages
defined herein. It is intended that these parameters be completely defined within this document before
use on a network. New features, Parameter Groups and Parameter definitions will be added over time; it
is anticipated that this document will continuously evolve as long as the SAE J1939 network is an active
Recommended Practice. Such growth will be implemented in such a way as to ensure backward
compatibility with earlier versions. At the time of initial publication, many of these growth areas are
identified but are yet to be defined. Such identification is provided so that the reader will be aware of
those additions that are already planned for the document. This procedure will define a number of
messages that may be configured, presently there are 16 configurable PDU 1 messages.
5.2 Overview of Configuration Services
The configuration messages and processes are intended to provide services needed to improve
utilization of bus bandwidth, facilitate organization of data within messages in a fashion that can allow
optimization of vehicle topology, and allow identification of this organization to 其他 CAs.
5.2.1 DEVELOPMENTAL HISTORY
These messages were originally proposed for Agricultural Applications, but have been harmonized and
standardized for all Industry Groups. In the Agricultural Industry specific example, self-propelled vehicles
with very different topologies need to use common parameters, so that third party vendors can know the
identity of parameters on the networks. But the message groupings must fit the vehicle topology in order
to have sufficient time to transmit all of the parameters. For this Agricultural need it is desired that the
source and destination addresses, as well as, the message configuration, be used to identify the data
SAE J1939-74 Issued SEP2004
- 6 -
within a particular message (just as source and destination address are needed to identify the data within
the proprietary A message identified in SAE J1939-21). These messages need to be configurable in the
sense that the groupings of parameters within a message were not predefined within one of the network
standard documents, but by the data within an其他 message (the Proprietary Message Configuration
Identification Message). The parameters being used are to be predefined within this network document,
just as 其他 parameters are defined within one of the 其他 network documents.
The Agricultural need was limited to destination specific messages and thus the original proposal was
tailored to that end. Several revisions studied allowing 其他 messages, but committee work has deemed
it best to maintain this restriction, that the only configurable messages are destination specific messages.
The new aspect of this document is the technique by which the grouping of certain parameters (defined
within this standard) can be arranged appropriately for the vehicle topology and then identified to 其他
network members by a configuration process, using the data content of a special initialization message.
This configuration process identifies the message being configured (by PGN), the parameters being sent
within said message (by SPN), as well as their placement within said message (by bit position). After
some discussion it was deemed that the feature could be handy for all Industry Groups and a working
group was sent out to develop a harmonized version.
5.2.2 HARMONIZATION
These messages have been harmonized for use in all Industry Groups. It is not the intent that all CAs will
use (or even need) these processes, but should they be used, this application document (SAE J1939-74)
is to be considered the driving document. This document defines the configuration process, the
configurable messages, the configuration messages and an associated set of certain parameters, which
are envisioned only for transmission within one of the configurable messages. There are 16 destination
specific messages (5.3.3), which are labeled as proprietarily configurable (5.3.1.5.1). These messages
may only include parameters from this application document (in 其他 words parameters from the 其他
SAE J1939 documents are not to be sent via the configurable messages at this time, see also 5.3.1.2 and
5.3.1.5). Transmission of the Configuration Identification Message (5.3.1) is the means used to identify
the data within one of these messages. Transmission of the Configuration Identification Message is
required if using any configurable messages. This is to provide the information about each message抯
contents to potential receivers as the Agricultural Industry Group desired.
5.2.3 OPERATION AND RELATED REQUIREMENTS
This configuration is not meant to be a dynamic process but rather is normally expected to be alterable
only at initialization. In fact in most systems the topology will be stable and hence the configuration will
likely not 改变 from one ignition cycle (power-up of the system) to an其他 (5.2.3.4). It is required that
CAs receiving configured messages check the NAMEs of the CA configuring the particular messages and
verify that they have not 改变d since a complete configuration list was received for each particular
message. If a NAME 改变 is detected then the complete configuration list for the particular message
should be requested. It is also required that CAs on an agricultural implement bus must maintain the
latest configuration while powered down (this is just like the current addresses association requirement of
all network members of an agricultural implement bus). For this reason and since it is desired to have the
quickest possible initialization process, there exists a bit parameter (5.3.1.7) that identifies that only the
data relevant to the first configured parameter (by SPN) is being identified with a Configuration
Identification Message. This is used so that the software may verify that a given message still comes
from a particular CA. (The reasoning here is that it is highly unlikely that a CA with the same NAME of
Controller Application parameter (SPN 2848) will be transmitting a message with a particular configured
message containing the same first parameter but with differences in the remainder of the message and
SAE J1939-74 Issued SEP2004
- 7 -
without knowing about it. Hence, this partial "Claim" will suffice to show 其他s on the network whether
the list of messages in their memory is still usable). This form is to be used on each power-up event for
each CA transmitting a configurable message. Should a receiver note that the NAME of the source, the
number of parameters or the location of a parameter does not match what is contained within it抯 own
memory then it should request the complete configuration identification between that CA and itself.
Should a transmitting CA know that it has 改变d (or will 改变) the message content of a configured
message, it should send (re-send) the complete new configuration identification for that message,
whether it is at start-up or during operation. Should the location of individual specific SPNs be needed
after a network is running, the Parameter Locate message (5.3.2) can be used. Should a complete
configuration between any two CAs be needed, a destination specific 'Request for' of the PGN of the
Configuration Identification Message can be used. The complete configuration of the specific message
(identified by PGN) from that particular source would then be transmitted upon the network.
5.2.3.1 Effects Upon Request Messages
For a CA seeking to find the configuration of messages on a network (necessary when for example it has
powered up separately from the rest of the network), there are two choices. It may send a 揜equest for?
(PGN 59904, see SAE J1939-21) the PGN of the Configuration Identification Message or it may send a
Request for Complete Configurable Message Set. A CA might also need the data from one of the
configurable messages, which is found by sending a 慠equest For?the PGN of Any of the Configurable
Messages. The rules for these cases are outlined in the following sections.
5.2.3.1.1 Global Request for PGN of Configuration Identification Message
A global 慠equest for?the PGN of the Configuration Identification Message is intended to cause all CAs
that transmit a configurable message to send only the shortened Configuration Identification Message
(where only the first SPN is identified (5.3.1.7)) for the configurable messages that they transmit,
regardless of source of the request. These messages should be sent exactly as at power-up. A response
is required for a 慠equest for?message for the PGN of the Configuration Identification Message. (If a tool
(or 其他 CA) should need to obtain the complete configuration on a vehicle, it should use the Request for
Complete Configurable Message Set message (5.3.3 & 5.2.3.1.3)).
5.2.3.1.2 Directed Request for PGN of Configuration Identification Message
A 慠equest for?the PGN of the Configuration Identification Message directed to a specific address is
intended to cause the CA at that address to transmit (or answer with) the complete sequence of
configuration identification messages for all of the configured messages that said destination sends to the
source of the request. Hence it is preferred that the 'Request for Configuration Identification Message' be
sent only to one specific destination at a time. (If a tool (or 其他 CA) should need to obtain the complete
configuration on a vehicle, it should use the Request for Complete Configurable Message Set message
(5.3.3 & 5.2.3.1.3)).
5.2.3.1.3 Request for Complete Configurable Message Set
There exists a separate message (5.3.3) designed to cause all CAs to respond with the complete
sequence of configuration identification messages for the configurable messages that they send. The
request may be for all configurable messages sent or a particular one, identified by PGN (5.3.3.2),
controlled by the parameter, Message Selection Control (5.3.3.1). If a tool (or 其他 CA) is using this
message to obtain the complete configuration on a vehicle, it must then also listen for all Configuration
Identification Messages regardless of the actual destination address of the Configuration Identification
Message. This is required since each of the Proprietarily Configured messages may be for a CA 其他
SAE J1939-74 Issued SEP2004
- 8 -
than said Tool, and hence the Configuration Identification Messages will not be directed to said Tool.
(Note that this requirement is only for a tool (or an其他 CA needing the complete configurable set for the
vehicle) and normal CAs need understand only what is sent to it by any of the 其他 CAs.)
5.2.3.1.4 慠equest For?the PGN of Any of the Configurable Messages
A 慠equest for?message for the PGN of any of the Configurable Messages (5.3.3) is intended to function
just like a 慠equest for?any PGN defined elsewhere within SAE J1939. The CA receiving the 慠equest for?
the PGN of one of the Configurable Messages should then send the message identified by said PGN and
the data values appropriate for that message (providing of course that it sends said configurable
message).
5.2.3.1.5 Software Mapping of Message Configurations
Configuration maps should be made a function of the NAME of Address Claimed of the CAs (this is not to
say that the parameter NAME of Controller Application (SPN 2848) should be the index or pointer but
only that an association should be maintained with the NAME of Address Claimed parameter). The
address tables may be used to translate from network address to a particular function by this association
with NAME of Address Claimed parameter. This way it is possible for a CA to recognize that it has been
moved or that an其他 CA has been added or 改变d. Then the CA may appropriately request the
configuration of the new network. Note that a CA need only request a configuration update if a CA that it
communicates with using a configurable message has been 改变d (in 其他 words if the 改变 is in a
CA that is not communicated with, there is no need to form a configuration map).
5.2.3.1.6 Time-Outs Needed for Request for PGN of the Configuration Identification Message
Any CA which plans to make requests for the PGN of the Configuration Identification Message will need
to have a time-out mechanism to determine when the list of configuration identification messages has
ended. This is due in part to the fact that the number of configured messages is not known prior to
sending the request. The value of this time-out will need to be based upon the actual application being
handled and is not identified within this document.
5.2.3.2 Additional CA Requirements
The length of each parameter must be known from the SLOT assignment in the definition of that
particular parameter. This requires that any CA that is going to use a particular parameter must contain
the SLOT data for that parameter.
5.2.3.3 Application for New Parameter Definitions
All parameters need to be requested, defined, and assigned SPNs just as is currently done (see SAE
J1939 no-dash appendices). The placement of the new parameter(s) within this document (by whatever
database means) will identify that the new parameter may be used within the Proprietarily Configurable
messages. CAs using these parameters will need additional application software to handle the calculation
work which must be done to determine the location of the particular parameter within the message and
whether the total length of the configured message will be such that transport protocol will be required
(5.3.1.6).
SAE J1939-74 Issued SEP2004
- 9 -
5.2.3.4 Continuity Across Power Cycles
It is required that any CA sending or using one of the configured messages remember the configuration
across power cycles.
5.3 The Configuration Service
The Proprietarily Configurable Messaging application includes a service to identify the configuration of
messages, including the association of parameters within the particular message. (Note: This means to
identify by listing the details of what exists and is not a capability to command (or force) a particular
configuration).
5.3.1 CONFIGURATION IDENTIFICATION MESSAGE
This is the message used to identify the data content (by SPN) of one of the configurable messages
(identified by PGN). Configuration is normally a vehicle build occurrence with a short Initialization
procedure to enable Controller Applications, CAs (see SAE J1939-81), to verify that they are operating on
the same network with the same 其他 CAs as when they last operated (see 5.2.3.4 & 5.3.1.7 for
discussion). The Configuration Identification message identifies the configuration (or location within a
message) of only one parameter at a time. Therefore, it takes 'n' transmissions of this Configuration
Identification Message to completely identify the configuration of one of the Configurable Messages in
which 'n' parameters will be transmitted.
This message is also used to identify the location within a message of any particular parameter (identified
by SPN), in response to the Parameter Locate Message (5.3.2). In this role, a Configuration Identification
message is sent whenever a CA receives a Parameter Locate Message for a parameter that it is
transmitting.
The rules regarding use of this message are in 5.3.1.9. The rules regarding interaction between this
message and the 慠equest for PGN?(PGN 59904, see SAE J1939-21) are outlined in 5.2.3.1.
Remember that since the Destination Address is used to help define (interpret) the data content, the
Configuration Identification Messages is NOT necessarily sent to the address from which the 慠equest
for?message was sent. Since this would effectively 改变 the configuration and meaning of these
Proprietarily Configured Messages, the destination of each Configuration Identification Message must be
the address to which the configured message will normally be sent.
Transmission Rate: As needed
Data Length: 8
Data Page: 0
PDU Format: 176
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 45056
CONFIGURATION_IDENTIFICATION_MESSAGE
Byte: 1-3 PGN Of Message Being Configured 5.3.1.1
(bit order per SAE J1939-21 Table 2)
SAE J1939-74 Issued SEP2004
- 10 -
Byte: 4 bits 8-1 Parameter Being Included, 8 least significant bits 5.3.1.2
(most significant at bit 8)
Byte: 5 bits 8-1 Parameter Being Included, second byte
(most significant at bit 8)
Byte: 6 bits 8-6 Parameter Being Included, 3 most significant bits
(most significant at bit 8)
bits 5-1 Position Of Configured Parameter 5.3.1.3
(most significant at bit 5)
Byte: 7 bit 8 Message Will Be Used Proprietarily 5.3.1.5
bit 7 Message Will Use Transport Protocol 5.3.1.6
bit 6 First Parameter Only Being Identified 5.3.1.7
bits 5-1 Number Of Parameters Included 5.3.1.4
(most significant at bit 5)
Byte: 8 Starting Bit For This Parameter 5.3.1.8
5.3.1.1 PGN of Message Being Configured
This is the PGN of the message whose configuration is being identified by this Configuration Identification
Message. A 3 byte slot is used.
Data Length: 24 bits (3 bytes)
Resolution: 1 message/count
Data Range: (16 Numeric values, one for each configurable message, to be selected by database
after ballot approval from the range 0, 256, ?61184, 61440, 61441, ?65535, 65536,
65792, ?126720, 126976, 126977, ?131071 ?i.e. Only 8672 values are
available/valid even though 24 bits)
Type: Measured
Suspect Parameter Number: 3146
Reference: 5.3.1
5.3.1.2 Parameter Being Included
This is the SPN of the parameter whose location is presently being identified for grouping into the
message whose PGN is in this Configuration Identification Message. The 19 bit SPN slot is to be used
(with a bit arrangement as in SAE J1939-73 diagnostics). The least significant bit is to be in data bit 25 of
the message (i.e. the lowest bit of data byte 4), with eight bits in byte 4, the next 8 bits in byte 5, and the
final 3 bits in byte 6, with the most significant bit to be in data bit 48 (i.e. the 8th bit of data byte 6). (Note:
This leaves bits 1 through 5 of data byte 6 for assignment to 其他 parameters, see 5.3.1.3). The list of
parameters that may be located is contained within Appendix C. (This again indicates that the
configurable messages are, at this time, not to be used with parameters from 其他 of the SAE J1939
documents, see also 5.2.2 and 5.3.1.5.)
Data Length: 19 bits
Resolution: 1 parameter(or object)/count
SAE J1939-74 Issued SEP2004
- 11 -
Data Range: 0 to 524,287
Type: Measured
Suspect Parameter Number: 3147
Reference: 5.3.1
5.3.1.3 Position of Configured Parameter
This is a number identifying a particular parameter抯 position within a configured message in particular for
differentiating the parameter (identified by SPN) whose location is presently being identified from the
其他 parameters which will be grouped into the message whose PGN is in this Configuration
Identification Message. It is used to verify that all of the parameters to be included within the message
being configured have been received. A 5 bit slot with the values 0 and 31 is NOT allowed (0, since it
would imply no SPNs and 31, since it would imply an unknown number).
Data Length: 5 bits
Resolution: 1 item/count
Data Range: 1 to 30
Type: Measured
Suspect Parameter Number: 3148
Reference: 5.3.1
5.3.1.4 Number of Parameters Included
This is the number of parameters, which will be grouped into the message whose PGN is in this
Configuration Identification Message. It is used in the verification that all of the SPNs to be included within
the message being configured have been received. A 5 bit slot with 0 and 31 are NOT allowed (0, since it
would imply this is not a member and 31, since it would imply that the member is not known - both poor
choices).
Data Length: 5 bits
Resolution: 1 parameter/count
Data Range: 1 to 30
Type: Measured
Suspect Parameter Number: 3152
Reference: 5.3.1
5.3.1.5 Message Will Be Used Proprietarily
This is a single bit flag used to indicate that the message being configured is a member of the set of
destination specific proprietarily configurable messages, and that hence the Source Address and
Destination Address are needed to interpret the data as with the destination specific Proprietary A
message of SAE J1939-21. A single bit slot is needed. This parameter is necessary in case the
application is ever expanded to allow inclusion of parameters from 其他 SAE J1939 documents. Since
this is not presently allowed this parameter should always be set to a ?? (This again indicates that the
configurable messages are, at this time, not to be used with parameters from 其他 of the SAE J1939
documents, see also 5.2.2 and 5.3.1.2.)
SAE J1939-74 Issued SEP2004
- 12 -
Data Length: 1 bit
Resolution: n/a
Data Range: 1 ( 0 would be added should the committee ever decide to allow this application for
standard SAE J1939 parameters)
Type: Measured
Suspect Parameter Number: 3149
Reference: 5.3.1
5.3.1.5.1 Proprietarily Configured Message
A ??in this parameter signifies that the message being configured is a member of the set of destination
specific proprietarily configurable messages (presently the only option) and that the interpretation of the
data is to be based upon a combination of the source address, the destination address and the SPN of
the specific data item. Hence the only parameters, which may be used, are those identified within this
document. Also any CA wishing to use data from the message being configured must associate the
source and the destination addresses as well as the Configuration Identification Message for the desired
SPN within said configured message to obtain an interpretation of the data. Presently a ??is the only
option here and this parameter only exists to allow future expansion of this application should the
committee ever deem necessary.
5.3.1.5.2 Not Proprietarily Configured Message
This is identified only as the mechanism necessary to extend this application to all SAE J1939
parameters, should the committee ever deem necessary. A value of ??in this parameter would then be
used to signify that the parameters were not necessarily from within this document. Presently a value of
??is not allowed.
5.3.1.6 Message Will Use Transport Protocol
This is a single bit flag used to indicate that the message being configured is one that will use transport
protocol. This bit must be properly set by all CAs configuring messages, as some receivers may need to
know this (as opposed to being able to calculate), since the length of the SPN is not contained within the
Configuration Identification Message and receivers are only required to know the length of SPNs they are
using (i.e. NOT all existing SPNs), and hence may not be able to calculate how long any particular
message is going to be. A single bit slot is needed.
Data Length: 1 bit
Resolution: n/a
Data Range: 0 or 1
Type: Measured
Suspect Parameter Number: 3150
Reference: 5.3.1
5.3.1.6.1 Transport Required
A ??in this parameter signifies that the message being configured will require transport protocol.
SAE J1939-74 Issued SEP2004
- 13 -
5.3.1.6.2 Transport Not Required
A ??in this parameter signifies that the message being configured will NOT require transport protocol.
5.3.1.7 First Parameter Only Being Identified
This is a single bit, which is used to identify that only the first parameter that will be sent within one of the
Configurable Messages is being identified with a Configuration Identification Message. This form is to be
used on each power-up event for any CA. This function has been generated so that the software can
verify that a given message still comes from a particular CA but with the shortest possible initialization
times. Identification of the location of individual specific parameters can then be handled with the
Parameter Locate message (5.3.2).
Data Length: 1 bit
Resolution: n/a
Data Range: 0 or 1
Type: Measured
Suspect Parameter Number: 3151
Reference: 5.3.1
5.3.1.7.1 First Parameter Only
A ??in this parameter signifies that only the first parameter of the particular message being configured is
being identified with a Configuration Identification message. See use note in 5.3.1.7.2.1.
5.3.1.7.2 All Parameters Being Identified
A ??in this parameter signifies that all of the parameters that will be transmitted in the particular
configurable message, are being identified using a separate Configuration Identification message for
each parameter (identified by SPN).
5.3.1.7.2.1 Configuration Change
Should a transmitting CA know that it has 改变d message content it should send (re-send) the whole
configuration identification list, thus this parameter would be ?? whether at start-up or during operation.
5.3.1.8 Starting Bit for this Parameter
The bit position within the configurable message being identified by the PGN in bytes 1-3 that the least
significant bit of the data for the parameter, whose SPN is identified in bytes 4-6, is to occupy. This
parameter will use an 8 bit SLOT with range of 0 to 250. Bit numbering is detailed below (see 5.3.1.8.1).
Since this parameter identifies only the position of the least significant bit, it must be remembered that the
length is to already be in the CA抯 parameter database (see 5.3.1.9.2). This parameter is to be in data
byte 8 of the configuration message. (Note: While the data range maximum of 250 does not allow a fulllength
transport message to be generated it allows quite a long message, which was felt to be a suitable
compromise necessary to generate this service. Remember this service is about improving throughput
and an extremely long message certainly will not help that much).
SAE J1939-74 Issued SEP2004
- 14 -
Data Length: 8 bits (1 byte)
Resolution:
Data Range: 0 to 250
Type: Measured
Suspect Parameter Number: 3153
Reference: 5.3.1
5.3.1.8.1 Bit Numbering
The bit numbering within the data fields is defined with 1 for the least significant bit of the first data byte, 8
for the most significant bit of the first data byte, 9 for the least significant bit of the second data byte. .
.(continuing sequence) , 57 for the least significant bit of the eighth data byte, and 64 for the most
significant bit of the eighth data byte. For messages using SAE J1939 transport protocol the bit
numbering is the same (remember however that the first data byte (bits 1 through 8) of each transport
packet contains the sequence number). However for transport messages the complete bit identification is
the sequence number times the bit number within the packet less eight (SAE J1939-21 3.10.1.2
Sequence Numbers & 3.10.1.3 Packetization). (Also remember that bits 1 through 8 of each packet are
not available for data as they contain the sequence numbers). (see: Byte alignment requirements).
Byte 1
8 1
DLC
time
bits transmitted 1st bits transmitted last
CRC
16 9 56 49 64 57
Byte 2 Byte 7 Byte 8
Data Field
per -21 8 1
per -74
8 1 8 1 8 1
DATA FIELD BIT NUMBERING DRAWING FOR 5.3.1.8.1.
5.3.1.8.2 Bit Placement Within A Message
Bit placement should be sequential from the starting bit. For example an ?1?bit parameter with a starting
bit of 19 (message data byte 3 bit 3) should end (bit containing its MSB) at bit 29 (message data byte 4
bit 5).
Byte 2
16 9
time
(CRC )
24 17 32 25 48 33
Byte 3 Byte 4 Byte 5
per -21 8 1
per -74
8 1 8 1 8 1
19
LSbit MSbit
11 bit
parameter
6 5 4 3 2 1 11 10 9 8 7
29
( DLC)
parameter bit number
EXAMPLE FOR 5.3.1.8.2
SAE J1939-74 Issued SEP2004
- 15 -
5.3.1.8.3 Placing Undefined Bits Within a Message
Undefined bits may be placed between parameters within a configured message (although the DLC is to
be maintained at 8, see 5.4.1.2). By undefined bits it is meant, bits to which no parameter is associated.
Undefined bits should simply be ignored by any receivers of the particular configured message. Since
undefined bits have no particular parameter association they should have no meaning associated with
them.
This feature is used when it is desired to justify a particular parameter to a specific bit location within the
configured message. To accomplish this the user need simply start the particular parameter where
desired, leaving however many undefined bits between it and the previous parameter.
5.3.1.8.4 Configured Message Length
The length of any given configured message may be undeterminable to the CA(s) receiving it. This is
because the CAs are only required to know the length of any parameters (identified by SPN) that they
wish to receive and the last parameter may not be one they want to receive. Hence, the total message
length will be is effectively unknown to them. Thus application software for configurable messaging does
not need to check for length. Also any software that was cross linking layers and being used to check for
length should be modified (updated) to recognize this possibility. Remember that data length of a
message is always a number of bytes since the protocol controllers have no provision to send part of a
byte.
5.3.1.9 Requirements Related to Configuration Identification Message
The Configuration Identification message (5.3.1) is used to identify the data content (by SPN) of any of
the configurable messages (identified by their PGN). This identification is handled by reporting the
location of one parameter within one message with each Configuration Identification Message. For this
application to be useful some requirements (restrictions) must be enforced on all. Some SAE J1939
documents allow non-interference to be ex改变d with compliance. This document, however, must be
interpreted more literally and hence any failure to conform exactly is considered non-compliance. Since
features or parameters may be added to this application, no CA should use this application (or its
parameters and messages) without having provisions for field updating of its application software to the
newest application level of the document.
5.3.1.9.1 When Must a Configuration Identification Message Be Used
The Configuration Identification is required whenever a CA is using any of the Configurable Messages
(5.4 & 5.3). When identifying configurable messages using the word 憄roprietarily? it is meant that the
data content of the particular configurable message can only be fully identified by combining the source
and the destination addresses of the particular configurable message with the data content of all the
configuration identification messages that have been sent for that particular configurable message.
5.3.1.9.2 CA Parameter Database
Receivers planning to use Configurable Messaging are required to know the SLOT of the parameters
they are expecting to use. (They are not required to know the length of all existing parameters).
SAE J1939-74 Issued SEP2004
- 16 -
5.3.2 PARAMETER LOCATE MESSAGE
This message is designed to cause 其他 CAs to respond with the identity of any message that they send
in which the particular parameter (identified by specific SPN) is contained. A command byte (5.3.2.2)
within this message is used to select the function to identify the location of a parameter. Other functions
may be added later (in fact the remainder of the command byte is reserved). The destination to which this
message is sent is to determine who answers. If the 慻lobal?destination address is used then all CAs
(supporting this function of course) that know and send the identified parameter will answer with a
CONFIGURATION IDENTIFICATION MESSAGE identifying any message, where this parameter is
presently being sent within 200 mS of the receipt of the Parameter Locate Message. If the parameter is
not being sent then there will be no response sent. In light of this and the fact that the number messages
containing a given SPN may not be known there must be time-outs (250 mS) in the CA sending the
Parameter Locate Message to identify that no one is going to answer and/or that the answering is done. If
this message is sent to a specific destination address then only the CA at that address should answer.
Transmission Rate: As needed
Data Length: 8
Data Page: 0
PDU Format: 175
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 44800
PARAMETER_LOCATE
Byte: 1 bits 8-1 Parameter to be located, 8 least significant bits 5.3.2.1
(most significant at bit 8)
Byte: 2 bits 8-1 Parameter to be located, second byte of SPN
(most significant at bit 8)
Byte: 3 bits 8-6 Parameter to be located, 3 most significant bits
(most significant at bit 8)
bits 5-1 Reserved (to be ?11112?
Byte: 4 bits 8-1 Reserved (to be sent as ?11111112?
Byte: 5 bits 8-1 Reserved (to be sent as ?11111112?
Byte: 6 bits 8-1 Reserved (to be sent as ?11111112?
Byte: 7 bits 8-1 Reserved (to be sent as ?11111112?
Byte: 8 bits 8-1 Parameter Locate Command 5.3.2.2
5.3.2.1 Parameter to be Located
This is the parameter, identified by SPN, that it is desired to locate or initiate the transmission of. Locating
implies identifying any message from the given source (i.e. the destination of this Parameter LOCATE
MESSAGE, all 其他 CAs when 慻lobal?address is used) that contains this particular parameter.
Data Length: 19 bit
Resolution: 1 parameter (or object)/count
SAE J1939-74 Issued SEP2004
- 17 -
Data Range: 0 to 524,287
Type: Measured
Suspect Parameter Number: 3154
Reference: 5.3.2
5.3.2.2 Parameter Locate Command
A byte used to identify the particular command that the Parameter Locate message is presently being
used for.
Data Length: 8 bit
Resolution: 1 command/count
Data Range: 0 with 1 to 250 reserved by SAE
Type: Measured
Suspect Parameter Number: 3155
Reference: 5.3.2
5.3.2.2.1 Identify Parameter抯 Location
This is the state of the Parameter Locate Command parameter (value of ?? used to identify that the
intent of this Parameter Locate message is to request that the position of a particular parameter
(identified by SPN) within any transmitted message being used by the identified destination. This value is
to mean that the position of said parameter within any message where it is presently being transmitted by
the destination of this Parameter Locate message will be identified using a Configuration Identification
message. The destination of this particular Parameter Locate message will identify whether all (the global
destination address)其他 CAs, which contain the particular parameter or only a specific CA should
answer with the messages.
5.3.3 REQUEST FOR COMPLETE CONFIGURABLE MESSAGE SET
This message is designed to cause all CAs to respond with the complete sequence of configuration
identification messages for a particular one or all of the configurable messages that they send. The
choice of all configurable messages or a particular one, identified by PGN, is controlled by the Message
Selection Control parameter (5.3.3.1). A receiving CA which uses no configurable messages is not
required to take any action in response to this request. The requesting CA must build the message set
table and consider that any network CAs not heard from are not using this service.
Transmission Rate: As needed
Data Length: 8
Data Page: 0
PDU Format: 253
PDU Specific: 176
Default Priority: 6
Parameter Group Number: 64941
SAE J1939-74 Issued SEP2004
- 18 -
REQUEST_FOR_COMPLETE_CONFIGURABLE_MESSAGE_SET
Byte: 1 bits 8-1 Message selection control 5.3.3.1
Byte: 2-4 PGN of configurable message desired 5.3.3.2
(bit order per SAE J1939-21 Table 2)
Byte: 5 bits 8-1 Reserved (to be sent as ?11111112?
Byte: 6 bits 8-1 Reserved (to be sent as ?11111112?
Byte: 7 bits 8-1 Reserved (to be sent as ?11111112?
Byte: 8 bits 8-1 Reserved (to be sent as ?11111112?
5.3.3.1 Message Selection Control
This is the parameter that identifies whether the configuration set is desired for a particular configurable
message or for all of the configurable messages.
Data Length: 8 bits
Resolution: 1 choice (or object)/count
Data Range: 0 and 1
Type: Measured
Suspect Parameter Number: 3329
Reference: 5.3.3
5.3.3.1.1 Identify All Configurable Messages
A ??in this parameter signifies that it is desired to identify the configuration for all of the configurable
messages in use by the receiver. The PGN of Configurable Message Desired parameter (5.3.3.2) is
meaningless for this case and shall be ignored by any receiver.
5.3.3.1.2 Identify Particular Configurable Message
A ??in this parameter signifies that it is desired to identify the configuration for a particular configurable
message. That particular message will be identified by the PGN in the PGN of Configurable Message
Desired parameter, 5.3.3.2.
5.3.3.2 PGN of Configurable Message Desired
This is the PGN of the configurable message whose configuration is being requested by this Request for
Complete Configurable Message Set. A 3 byte slot is used. The all 1抯 value shall be transmitted when
the request is for all configurable messages (5.3.3.1.1), 其他wise the PGN of one of the configurable
messages should be used. Should an invalid PGN be received the complete set for all of the
configurable messages in use should be sent.
Data Length: 24 bits (3 bytes)
Resolution: 1 message/count
SAE J1939-74 Issued SEP2004
- 19 -
Data Range: (17 Numeric values, one for each configurable message, to be selected by database
after ballot approval from the range 0, 256, ?61184, 61440, 61441, ?65535, 65536,
65792, ?126720, 126976, 126977, ?131071 ?i.e. Only 8672 values are
available/valid even though 24 bits and FFFFFF16)
Type: Measured
Suspect Parameter Number: 3330
Reference: 5.3.3
5.4 The Set of Destination Specific Proprietarily Configurable Messages
This is the set of PDU type 1 messages that may be used in a proprietary fashion for sending only
parameters defined within this SAE J1939 document (note: more parameters may be added at a later
date). Configured messages from this set will be identified on the network using a Configuration
Identification Message. Also note that since the use of these messages is destination specific the use of
the global destination address (value 255) would not make sense and is hence not allowed. Should a
receiving device detect one of these messages directed to the global address, it should consider the
message meaningless and not to be processed (in 其他 words just dispose of it).
5.4.1 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 1
The first message of the set assigned for use as a proprietarily configurable destination specific
message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 177
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 45312
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_1
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.1.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
SAE J1939-74 Issued SEP2004
- 20 -
5.4.1.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.2 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 2
This is the second message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 178
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 45568
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_2
Byte: 1-8 As defined within the appropriate Configuration Identification Message(s)
5.4.2.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.2.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
SAE J1939-74 Issued SEP2004
- 21 -
5.4.3 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 3
This is the third message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 179
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 45824
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_3
Byte: 1-8 As defined within the appropriate Configuration Identification Message(s)
5.4.3.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.3.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.4 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 4
This is the fourth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 180
PDU Specific: DA
SAE J1939-74 Issued SEP2004
- 22 -
Default Priority: 6
Parameter Group Number: 46080
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_4
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.4.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.4.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.5 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 5
This is the fifth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 181
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 46336
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_5
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
SAE J1939-74 Issued SEP2004
- 23 -
5.4.5.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.5.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.6 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 6
This is the sixth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 182
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 46592
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_6
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.6.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
SAE J1939-74 Issued SEP2004
- 24 -
5.4.6.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.7 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 7
This is the seventh message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 183
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 46848
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_7
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.7.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.7.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
SAE J1939-74 Issued SEP2004
- 25 -
5.4.8 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 8
This is the eighth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 184
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 47104
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_8
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.8.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.8.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.9 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 9
This is the ninth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 185
PDU Specific: DA
Default Priority: 6
SAE J1939-74 Issued SEP2004
- 26 -
Parameter Group Number: 47360
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_9
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.9.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.9.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.10 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 10
This is the tenth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 186
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 47616
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_10
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.10.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
SAE J1939-74 Issued SEP2004
- 27 -
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.10.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.11 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 11
This is the eleventh message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 187
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 47872
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_11
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.11.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.11.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
SAE J1939-74 Issued SEP2004
- 28 -
5.4.12 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 12
This is the twelfth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 188
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 48128
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_12
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.12.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.12.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.13 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 13
This is the thirteenth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 189
PDU Specific: DA
Default Priority: 6
SAE J1939-74 Issued SEP2004
- 29 -
Parameter Group Number: 48384
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_13
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.13.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.13.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.14 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 14
This is the fourteenth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 190
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 48640
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_14
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.14.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
SAE J1939-74 Issued SEP2004
- 30 -
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.14.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.4.15 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 15
This is the fifteenth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 191
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 48896
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_15
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.15.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.15.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
SAE J1939-74 Issued SEP2004
- 31 -
5.4.16 DESTINATION SPECIFIC PROPRIETARILY CONFIGURABLE MESSAGE 16
This is the sixteenth message in the set of messages assigned for use as a proprietarily configurable
destination specific message.
Transmission Rate: As needed
Data Length: 8 to n (based on Configuration Identification Message, see 5.3.1.6)
Data Page: 0
PDU Format: 192
PDU Specific: DA
Default Priority: 6
Parameter Group Number: 49152
DESTINATION_SPECIFIC_PROPRIETARILY_CONFIGURABLE_MESSAGE_16
Byte: 1-n As defined within the appropriate Configuration Identification Message(s)
5.4.16.1 Parameter Content of Destination Specific Proprietarily Configurable Messages
The parameters sent within any of the Proprietarily Configurable Messages are identified within a set of
Configuration Identification Messages each of which contains the PGN of the particular Destination
Specific Proprietarily Configurable Message. Each of the Configuration Identification Messages also
contains the location information for a single SPN. Thus a CA sending a particular Destination Specific
Proprietarily Configurable Message with 憂?parameters will need to send 憂?Configuration Identification
Messages to any CA it wishes to decode said Destination Specific Proprietarily Configurable Message.
Remember that only parameters from within this document are to be included within any Destination
Specific Proprietarily Configurable Message (presently the committee has chosen to not allow
configurable messaging with parameters from 其他 SAE J1939 document(s)).
5.4.16.2 DLC for Destination Specific Proprietarily Configurable Messages
The minimum data length of each of the Destination Specific Proprietarily Configurable Messages is to be
8. Hence, the DLC will be 8. (Remember the DLC is the packet data length and not the message data
length.) Any bits within the message which have not had parameters associated shall be sent as ??
(5.3.1.8.3). This is the most general form found for 其他 SAE J1939 messages, although there are a few
special cases where the DLC is 其他 than 8. The packet DLC will be 8, even when transport protocol is
used, because the total message data length exceeds 8 (see 5.3.1.6).
5.5 The Set of Parameters for Use Within the Configurable Messages
The set of parameters available for use within the Configurable messages is contained within Appendix
C. Certain operational rules still apply to these parameters just like any 其他s from 其他 SAE J1939
documents. When one of the parameters from this set is used, it will be transmitted on the network in one
of the Configurable messages and its location within said message will have been identified on the
network using the Configuration Identification Message.
PREPARED BY THE SAE TRUCK AND BUS CONTROL AND COMMUNICATIONS NETWORK
SUBCOMMITTEE OF THE SAE TRUCK AND BUS ELECTRICAL AND ELECTRONICS COMMITTEE
SAE J1939-74 Issued SEP2004
- 32 -
APPENDIX A
ASSUMPTIONS USED TO DESIGN CONFIGURABLE MESSAGING
A.1 Assumptions Used In the Design of Configurable Messaging
A.1.1 Some applications require pre-defined parameters but must have groupings (messages) that can
be reconfigured when the vehicle is 慴uilt?
A.1.2 Message reconfiguration does not need to be dynamic but there is no need to eliminate the
possibility if not required simply to complete the design.
A.1.3 Some will desire to re-group existing parameters, while 其他s will wish to re-group only members
of a special set. Hence allow for both if possible.
A.1.4 Some will desire proprietary message definition and some will not, so again allow both if possible.
A.1.4.1 To allow proprietary identification requires that the 慽dentification?message to be destination
specific so choose that.
A.1.5 Some will desire destination specific and some global destination so again allow both. However
since the interpretation of a global proprietary message would have to be the same to all CAs it
reduces to the same case as the global destination non-proprietary message.
A.1.5.1 Hence need three set of messages.
A.1.6 Since regrouping is essentially a time improvement scheme there is no real need for a large
number of messages or for extremely long messages. They both kind of defeat the purpose.
A.1.6.1 So as a first guess try 16 messages in each set of messages.
A.1.7 Some will desire this process, while 其他s will hope to avoid it entirely, so assign it to an entirely
new application document.
A.1.8 Some will wish to place SPNs at specific bit boundaries within the message so as to ease
software in some fashion, so allow 憉nused?bit to separate SPNs.
A.1.9 Since will need to know things (length, SLOT,etc.) about an SPN to use it, this might as well be a
requirement for use of this process and it can be designed that way.
A.1.10 Once the capability to identify where an SPN is sent , why not have a means of asking where
they are being sent. Hence create a 慙ocate SPN?message, which can request the identification
of any message in which the particular SPN is presently being sent.
A.1.11 While there is space within the message structure to allow for 其他 functions within the SPN
Locate message it is felt by the working group that no 其他 functions should be pursued at this
time.
SAE J1939-74 Issued SEP2004
- 33 -
A.1.12 Configuration maps should be made with an association of function, of CA, and of the NAME of
Address Claimed parameter using address tables to translate between network address and CA
NAME. (This is not to imply that the indexing structure of the software should use the NAME of
Address Claimed parameter but only that the expansion along a particular completed path
through the indexing structure should identify a specific NAME of Address Claimed). This way it
is possible for a CA to recognize that it has been moved or that an其他 CA has been 改变d
and then appropriately request the configuration of the new network. Note that a CA need only
request a configuration update if a CA that it communicates with using a configurable message
has been 改变d (in 其他 words if the 改变 is in a CA that is not communicated with, there is
no need to form a configuration map).
A.1.13 A separate message has been added to allow the determination of the complete set of
configurable messages in use on the vehicle.
SAE J1939-74 Issued SEP2004
- 34 -
APPENDIX B
APPLICATION RULES REGARDING CONFIGURABLE MESSAGING
B.1 General Rules
The following general rules must be adhered to:
B.1.1 When a Configuration Identification Message is sent to the 慻lobal?destination address the
configuration must remain independent of the destination address. This should in general only be
done with a configurable message from either the set of destination specific non-proprietarily
configurable messages or the set of global destination non-proprietarily configurable messages.
B.1.2 Messages should in general only be sent to a specific destination when they are from the set of
destination specific proprietarily configurable messages.
B.1.3 For a CA seeking to find the configuration of messages on a network, when it has powered up
separately from the rest of the network (such as a tool being plugged in), a Request for Complete
Configurable Message Set may be sent. If the configuration need only be verified then the
慠equest for Configuration Identification Message?can be sent to the global destination so that
everyone sending configurable messages answers with the shortened form (i.e. only the first
SPN for each of the configurable messages (see 5.3.1.7 & 5.2.3.1)).
B.1.4 A Tool sending a destination specific request for message for the PGN of the Configuration
Identification Message must watch for any Configuration Identification Messages sent on the
network. These Configuration Identification messages are to be sent to the normally intended
destinations address. There should also be the number of messages to the particular address
that there are SPNs in the Configured Message.
The tool may obtain the complete configuration of an operating vehicle by sending Request for Complete
Configurable Message Set on the network (remember this is not merely to all CAs, since any given CA
may have more than one address). The tool will need to maintain the association between the source and
destination addresses of any Configuration Identification Messages sent for members of the set of
Destination Specific Proprietarily Configurable Messages with the data, since the CA may be configuring
communications with CAs 其他 than the tool. Hence the messages may not have been addressed to the
tool, thus the destination address of the Configuration Identification Messages will not necessarily be the
tool抯 address.
B.1.5 If a Tool has made a Request for message of the PGN of the Configuration Identification
Message to the 慻lobal destination address? then the Tool will only see the Configuration
Identification Messages of the first SPN (5.3.1.7) of each of the Configured Messages used within
the network.
B.1.6 CAs sending configured messages must answer a Request for message for the PGN of the
Configuration Identification Message with all of the configurations that they use (see also
5.2.3.1.1).
B.2 Message Ex改变 Rules
Presently all ex改变 rules are outlined within the main sections of the document and are not repeated
here.
SAE J1939-74 Issued SEP2004
- 35 -
APPENDIX C
PARAMETERS FOR CONFIGURABLE MESSAGING
C.1 General Items
The same general issues of SLOT, Type, Length, 操作Range, Units as identified in ?1 must be
adhered to for parameters for configurable messaging.
C.1.1 The parameter list is blank at this time. Parameters will be generated and added as refinements
are made to this document.
C.1.2 Messages should in general only be sent to a specific destination when they are from the set of
destination specific proprietarily configurable messages.
C.1.3 Parameters will be transmitted on the network in one of the Configurable messages with the
parameter location within said message being identified on the network using the Configuration
Identification Message.
C.2 Parameter Design Rules
Presently the rules to assist in creating a new parameter are in development.
C.3 Parameter List
Presently the parameter list is blank. Parameters will be generated and added as refinements are made
to this document.
SAE J1939-74 Issued SEP2004
Rationale
Not applicable.
Relationship of SAE Standard to ISO Standard
Not applicable.
Application
The SAE J1939 documents are intended for light, medium, and heavy-duty vehicles used on or off road
as well as appropriate stationary applications which use vehicle derived components (e.g. generator
sets). Vehicles of interest include, but are not limited to, on- and off-highway trucks and their trailers,
construction equipment, and agricultural equipment and implements.
The purpose of these documents is to provide an open inter连接 system for electronic systems. It is
the intention of these documents to allow Electronic Control Units to communicate with each 其他 by
providing a standard architecture.
This particular document, SAE J1939-74, describes the message structure for a set of messages which
enable the user to determine and announce to 其他s on the network, the parameter placement within a
particular message from the special set of messages defined within this document.
Reference Section
SAE J1939-Recommended Practice for a Serial Control and Communications Vehicle Network is the
parent document and should be referenced in general.
SAE J1939-21 Data Link Layer
SAE J1939-71 Vehicle Application Layer
SAE J1939-73 Application Layer - Diagnostics
SAE J1939-81 Network Management
ISO 11783 Tractors, machinery for agriculture and forestry Serial control and communications data
network
Developed by the SAE Truck and Bus Control and Communications Network Subcommittee
Sponsored by the SAE Truck and Bus Electrical and Electronics Committee
Copyright ?2004 SAE International
All rights reserved. No part of this publication may be reproduced, stored in a retrieval system or transmitted, in any form or by any means, electronic, mechanical, photocopying,
recording, or 其他wise, without the prior written permission of SAE.
TO PLACE A DOCUMENT ORDER: Tel: 877-606-7323 (inside USA and Canada)
J1939
收藏灵猫网
12522120
12522120
+86-14782588945
