Difference between revisions of "HANcoder/STM32/Blocks/UDS Init"
Line 1: | Line 1: | ||
{{HANcoder/block| | {{HANcoder/block| | ||
info= | info= | ||
− | + | This block initializes the Unified Diagnostic Services (UDS) module (ISO-14229) and the underlying CAN transport protocol (ISO-15765) module. | |
+ | |||
+ | The purposes of the UDS module in the blockset is three-fold: (1) to read and clear error codes, (2) to read/write memory, and (3) remote ECU reset. The first and third parts, error code access and remote ECU reset, are always available. The second part, memory access, can be locked with the block parameter "UDS seed/key required". | ||
+ | |||
+ | If "UDS seed/key required" is set to FALSE (unchecked), the UDS functionality is available through the services: | ||
+ | |||
+ | [[File:uds_default_session.png|400px]] | ||
+ | |||
+ | If "UDS seed/key required" is set to TRUE (checked), the UDS functionality is available through the services: | ||
+ | |||
+ | [[File:uds_extended_session.png|650px]] | ||
|blockImage=UDSInit.png | |blockImage=UDSInit.png | ||
+ | |maskImage=UDSInitMask.png | ||
− | + | }} | |
+ | == Outputs (outports) == | ||
+ | This block has a function call output that gets triggered during a seed/key sequence, when the UDS module needs a seed. The connected subsystem should contain a 'UDS Set Seed' block to give the seed back to the UDS module.[function call] | ||
− | | | + | == Block parameters == |
− | | | + | {| class="wikitable" |
− | | | + | |- |
− | | | + | ! style="width:150px" | Parameter |
− | | | + | ! Description |
− | | | + | |- |
− | | | + | | CAN Channel |
− | | | + | | |
+ | |- | ||
+ | | CAN Transmit ID | ||
+ | | | ||
+ | |- | ||
+ | | CAN Receive ID | ||
+ | | | ||
+ | |- | ||
+ | | TP Block size | ||
+ | | | ||
+ | |- | ||
+ | | TP STmin | ||
+ | | | ||
+ | |- | ||
+ | | TP Reception buffer size | ||
+ | | | ||
+ | |- | ||
+ | | UDS Transmit buffer size | ||
+ | | | ||
+ | |- | ||
+ | | UDS seed/key required | ||
+ | | | ||
+ | |} | ||
+ | == Examples == | ||
+ | [[HANcoder/Examples/UDS|UDS]] | ||
+ | {{HANcoder/BlockFooter| | ||
+ | |SeeAlso = [[HANcoder/UDS_Get_Key|UDS Get Key]] {{!}} [[HANcoder/UDS_Get_Seed|UDS Get Seed]] {{!}} [[HANcoder/UDS_Get_Seed_Event|UDS Get Seed Event]] {{!}} [[HANcoder/UDS_Init|UDS Init]] {{!}} [[HANcoder/UDS_Set_Key_Verified|UDS Set Key Verified]] {{!}} [[HANcoder/UDS_Set_Seed|UDS Set Seed]] {{!}} [[HANcoder/UDS_Verify_Key_Event|UDS Verify Key Event]] | ||
}} | }} |
Revision as of 09:34, 29 April 2017
Supported Targets: Olimexino, E407, P405
Contents
General information about UDS Init
This block initializes the Unified Diagnostic Services (UDS) module (ISO-14229) and the underlying CAN transport protocol (ISO-15765) module.
The purposes of the UDS module in the blockset is three-fold: (1) to read and clear error codes, (2) to read/write memory, and (3) remote ECU reset. The first and third parts, error code access and remote ECU reset, are always available. The second part, memory access, can be locked with the block parameter "UDS seed/key required".
If "UDS seed/key required" is set to FALSE (unchecked), the UDS functionality is available through the services:
If "UDS seed/key required" is set to TRUE (checked), the UDS functionality is available through the services:
Block
Mask
Outputs (outports)
This block has a function call output that gets triggered during a seed/key sequence, when the UDS module needs a seed. The connected subsystem should contain a 'UDS Set Seed' block to give the seed back to the UDS module.[function call]
Block parameters
Parameter | Description |
---|---|
CAN Channel | |
CAN Transmit ID | |
CAN Receive ID | |
TP Block size | |
TP STmin | |
TP Reception buffer size | |
UDS Transmit buffer size | |
UDS seed/key required |
Examples
See Also
UDS Get Key | UDS Get Seed | UDS Get Seed Event | UDS Init | UDS Set Key Verified | UDS Set Seed | UDS Verify Key Event