KWP 2000 on Samtec Hs+ Interface K Line

[Soma94]

Hi,

I am trying to Integrate an AMT, based on KWP 2000 Protocol along with the Samtec Hs+ Interface. The Hardware supports the ISO 9141 K-Line. I am stuck up with initialising the communication between the Module and the ECU. 

I have configured the Samtec Device to Samtec SamDiaX Active control (Automotive Software from Samtec) and created the .spa File. but yet the connection has not been established. Kindly guide me thru how to establish communication between Hardware Module and ECU

once if the communication has done, the LabVIEW program to correlate with the ECU will be done further. ( I have Used KWP 2000 on NI USB CAN from which I hope to build my own code on above concern but not the Communication part on K-Line). Thanks in Advance.

[Hooovahh]

You won't get much support from NI on this one.  You are using a 3rd party hardware for KWP 2000 protocol.  You said you did this with NI CAN and I'm guessing that was done with the Automotive Diagnostic Command Set toolkit which works only with NI hardware.  Writing your own software protocol on top of whatever drivers come with that hardware will likely be difficult.  The good news is there is some information on writing your own protocol from my blog post Part 8.  This shows the state machine used for ISO 15765, KWP 2000, UDS, and OBD protocols.  It also provides drivers and examples for using 3rd party hardware to perform this, by using the low level frame API.  If you must use that hardware, and you must use KWP 2000, you'll need to write a software layer like I did, or modify mine to work with your hardware.  This will involve replacing the frame read/write functions with the API for your hardware.

[Soma94]

You were right about myself using ADCS toolkit to NI Hardware.

But things are different on my case now. I already have the code using ActiveX to communicate with the Samtec Hardware. But before that I have to configure a file (.SPA format file) and load the same to hardware, so the communication between the ECU and hardware will start from then. The problem arise on configuring the .spa file which contains the details of the ECU and data transferring properties.

Thanks for your kind information and support