It seems you are trying to configure the DiagAlyser tool for vehicle diagnostics using specific CAN identifiers. If you are receiving a response only for the 09 session, this might imply that the tool is not correctly recognizing or handling the requests for the other sessions you mentioned.
Here are a few suggestions to resolve your issue:
-
Verify Protocol Settings: Ensure that your tool is set to use the correct protocol (e.g., ISO 15765-4 CAN for 11-bit identifiers).
-
Check the Identifier Settings: Make sure that both 7E0 (typically for request) and 7E8 (typically for response) are correctly set as the ECU identifiers.
-
Session Initialization: Some services or functions require that you first enter the correct diagnostic session before they can be accessed (e.g., session control could be needed to switch to extended diagnostic session before accessing certain services).
-
Security Access: Ensure that services requiring security access (such as 27 for security access) are properly initialized and the correct security key is being used.
-
Request Format: Double-check the format of the requests being sent, as incorrectly formatted requests might not receive a valid response from the ECU.
-
Software Documentation: Refer to the DiagAlyser's documentation or help resources for specific configuration guidance related to your use case.
If none of these steps resolve your issue, you might want to consult the support team for DiagAlyser or seek assistance from a community focused on automotive diagnostics.
