Automotive and Embedded Networks

cancel
Showing results for 
Search instead for 
Did you mean: 

UDS read incompatible clusters

Solved!
Go to solution
Highlighted

I'm trying to do a very simple application to read UDS ID's from my target, and am using the modified VI's (and very useful tutorial) from Hooovahh to do  a very simple test.

 

It is mentioned that you need to start a diagnostic session then feed the reference into the UDS config VIs, but they seem to be incompatible (see attached), do i need a different or other VI before?

 

Can anyone help get this going?

0 Kudos
Message 1 of 3
(585 Views)
Solution
Accepted by topic author djroseman
01-08-2019 07:08 AM

It looks like you are mixing my library, with NI's sorry if the icons are the same adding to the confusion, but they are in different libraries so that shouldn't be an issue.  I should have probably come up with my own icons but NI's worked so well and were familiar. 

 

Open context help (CTRL+H) and you should see the full path to the VI that your mouse hovers over.  It should become clear quickly that the first subVI you have is from the Automotive Diagnostic Command Set, and the next two subVIs are from my ISO15765 API.  Replace the second two with NI's and it should work.  My API doesn't currently support NI-CAN or NI-XNet hardware, it was really just meant to be a demonstration of how to do ISO15765 from pure G, and show how to do these types of commands from non-NI hardware.  


Unofficial Forum Rules and Guidelines - Hooovahh - LabVIEW Overlord
Interesting in learning all you can about automotive CAN bus communication? Checkout my 12 part CAN Blog series.
Checkout and help contribute to the community driven LabVIEW Wiki.

0 Kudos
Message 2 of 3
(561 Views)

That's the one! Thanks

0 Kudos
Message 3 of 3
(551 Views)