LIN Diagnostic Issue using LIN Stack

[chaitanya_kalyani]

Hello,

I am using processor expert mode, LIN stack(SDK_S32K1xx_15) and want to use diagnostics for S32K116 series controller.

I checked with Both IDE S32 Design Studio V2018 as well as V2.2.

For unconditional signal there is no issue but getting issue with diagnostic signal No Response Error getting.

For checking I am sending command Read By Identifier - LIN Product identification.

Code is enabled but control is not coming to the part of the code. Same thing tested and working with S12ZVL series controller.

Thank you in advance.

[danielmartynek]

Hello,

maybe you send a request with a wrong value of “Supplier ID” or “Function ID”.

S32DS configuration

Diagnostic request and response on the bus

Regards,

Daniel

[chaitanya_kalyani]

Hello @danielmartynek ,

Thank you for your response.

I checked still it is not getting response for diagnostics.

and my configuration is 

I am not getting where is the issue.

[danielmartynek]

Hello,

I'm sorry for the delayed response,

Could you please scope the the diagnostic request frame (3C) and the response frame (3D) by a logic analyzer on the LPUART pins?

This is an answer from the LIN Stack SW team:

Please make sure that the conditions below have been met:
- Tick on “User transport layer” and “Support diagnostic service” on tab “Network configuration”
- Configure with the correct value of “Supplier ID” and “Function ID” on tab “Node attribute definition”
- Re-generate configuration files and compile
- Call “ ld_init()” function before use diagnostic service.

Thank you,

BR, Daniel

[Francesco_Solito]

Good morning

I have the same issue (with S32DS 3.5 instead of 2018.R1). I followed the suggestions in this post, but I didn't solve. Did you solve your issue? Could you please share the solution?

Thank you in advance.

Kind regards,

Francesco Solito

[Francesco_Solito]

Hello

ld_init(LI0) was not present in the main.c of the example project "lin_slave_s32k118". Calling it before l_ifc_init(LI0) has solved the issue.

Kind regards,

Francesco