ISO15765:Blocks:Instance Definition

Woodward Custom ISO15765 Instance Definition

This block defines an instance of the ISO15765 protocol. UDS and J1979/ISO15031-5 are covered by this protocol.

Please read the ISO15765 topic for more information on using this protocol in a MotoHawk application.

Block ID

ISO15765 Instance Definition

Library

Woodward Custom ISO15765

Description

The instance block defines the communication interface, sessions, and the services handled by the application.

This block can support the ISO15765 protocol on more than one CAN channel, but not simultaneously. To specify operation on more than one CAN channel, set the mask parameter [#channel_name CAN Channel Name] to a cell array of strings like {'CAN_1' 'CAN_2'}. The first CAN channel to start receiving ISO15765 messages will get access to the protocol handler, while the other channel will be locked out. After a power off / power on of the module, or after a non-default session times out, a different CAN bus can gain access to the protocol handler.

The minimum receive and transmit buffer sizes are specified by the user. This size can be increased if Service 0x19 is specified in the handler based on the number of faults in the application. There are run time metrics for the maximum size used under System|Debug|ISO15765.

ODX Support

The Woodward Custom ISO15765 has the ability to export a description of the configured ISO15765 protocol in ASAM ODX format. See the ODX Export topic for more information.

Block Parameters

Parameter Field	Values	Comments/Description
Instance Name	String	Unique name for this instance of the protocol.
Definition Structure	Expression	Message structure that determines which sessions and services are supported
CAN Channel Name (more than 1 allowed)	string or cell array of strings	List of CAN resource names that will receive requests and transmit responses.
Rx ID Type	Numeric (1 or 0)	If 1, the Rx ID is treated as an extended ID (29 bit). If 0, then it is standard (11 bit).
Rx ID	Numeric	This is the ID that the CAN dispatcher will receive messages.
Tx ID Type	Numeric (1 or 0)	If 1, the Tx ID is treated as an extended ID (29 bit). If 0, then it is standard (11 bit).
Tx ID	Numeric	Responses will use this address for their ID.
Support Functional Address	checkbox	Specifies whether a CAN Slot will be created for the Function Rx ID.
Functional Rx ID	Numeric	Specifies the Receive ID used for functional queries.
Allow Calibratible CAN IDs (not implemented)	checkbox	In the initial version, CAN IDs will be constants.
Minimum Receive Buffer [7-4095 bytes]	Numeric	Specified the minimum receive buffer size. The minimum size is 7 bytes and the maximum size is 4095 bytes.
Minimum Transmit Buffer [7-4095 bytes]	Numeric	Specified the minimum transmit buffer size. The minimum size is 7 bytes and the maximum size is 4095 bytes.
Enforce Exact Request Lengths	checkbox	Choose whether to enforce exact lengths for incoming requests and respond with a negative response or to ignore extra data. Leaving this box unchecked allows for more flexibility. Minimum lengths are always enforced regardless of this setting.
OBD Fault Manger Custom Field Name for ISO15765-4 DTC	string	This field specifies the Custom Field (OBD Fault Manager) that will specify how to lookup the DTC value when transmitting responses to Services 0x3, 0x7, and 0xA. If this is not specified (i.e. left blank), then those services will not transmit any DTC information.
DTC Format for Service 0x19	Pull-down menu	This field specifies the format for constructing DTC values for Service 0x19 (only ISO 15031-6 is supported)
Custom Field Name for DTC (Required)	string	This field specifies the Custom Field (OBD Fault Manager) that will specify how to lookup the DTC value when transmitting responses to Services 0x19. This field is required if Service 0x19 is to be support.
Custom Field Name for Failure Category (Optional)	string	This field specifies the Custom Field (OBD Fault Manager) that will specify how to fill in the "Failure Categoroy" portion of the DTC value when transmitting responses to Services 0x19. This field is optional and the value "0" is used when left blank.
Custom Field Name for Failure Subtype (Optional)	string	This field specifies the Custom Field (OBD Fault Manager) that will specify how to fill in the "Failure Subtype" portion of the DTC value when transmitting responses to Services 0x19. This field is optional and the value "0" is used when left blank.