10-09-2017 03:48 AM
Hi,
It looks like that the VI Open Diagnostic.vi (ADCS) does not support UDS ISO14229 transport protocol. I can only chose form:
ISO TP Normal Mode
ISO TP Mixed Mode
VW 2.0
Diagnostic on IP
ISO TP LIN
Is there any way I can connect through UDS ISO14229?
K
10-09-2017 04:25 AM
The error I'm getting is:
Error -1074384605 occurred at Diag CAN open.vi Possible reason(s): NI-XNET: (Hex 0xBFF63123) You attempted to set a CAN arbitration ID with an invalid value. For example, a CAN standard arbitration ID supports only 11 bits. If you attempt to set a standard arbitration ID that uses more than 11 bits, this error is returned. Solution: Use a valid arbitration ID.
It looks like there is no support for 29bits frame size. Am I right?
10-11-2017 04:30 AM - edited 10-11-2017 04:32 AM
Playing further with ADCS toolkit I've got different message:
Error -8005 occurred at Diag CAN open.vi
Possible reason(s):
NI Automotive Diagnostics Command Set: A DLL required for communication with the ECU could not be loaded. Probably this library is not installed.
Could it be because ADCS is installed only for evaluation?
K.
10-11-2017 07:57 AM
I'll let someone more familiar with the inner workings of ADCS talk about the DLL loading, and extended ID modes.
But one option you might have if you have the time, is wrap your own ISO 15765 protocol in pure LabVIEW. With this you can get around any hard limitations that you might be seeing if ID range is an issue.
In Part 8 of my CAN blog I talk about the ISO 15765 protocol which is at the core of ADCS. I also provide some example code on how to do the same functions as ADCS, with generic CAN hardware, reading and writing raw frames. If you go this route you'll have full control over what goes out and comes back instead of relying on the (somewhat) black box of NI's toolkit.
Unofficial Forum Rules and Guidelines
Get going with G! - LabVIEW Wiki.
17 Part Blog on Automotive CAN bus. - Hooovahh - LabVIEW Overlord