What do the NI Automotive Diagnostic Command Set & ECU Measurement software packages really bring?

[jonathanupr]

I am looking at doing some CAN programming for the J1939 and J1708/1587 protocols.  Would the NI Automotive Diagnostic Command Set & ECU Measurement software modules even be necessary?

What are the benefits of both modules?

[pflores]

Just for reference, look here for comments on the J1939 and J1708/1587 protocols.

The ECU Measurement and Calibration Toolkit provides a helpful API for interfacing and designing an ECU. In particular, it provides high-level, easy-to-use functions based on the Universal Measurement and Calibration Protocol (XCP) and CAN Calibration Protocol (CCP). A more detailed explanation of what is included and when it should be used can be found in Chapter 1 of the ECU Measurement and Calibration Toolkit User Manual.

Automotive Diagnostic Command Set

From the overview section of the product page: "NI ADCS is suitable for a range of automotive diagnostic applications that typically involve reading and writing parameters, accessing diagnostic trouble codes (DTCs), flashing ECU firmware, and initiating ECU diagnostic test modes... ADCS benefits applications such as ECU firmware flashing tools, DTC reading and logging, ECU diagnostic mode interfacing, and live diagnostic variable monitoring and logging for on-road tests."

Hope this helps...

[Soma94]

Hi,

I am a newbie to LabVIEW CAN Communication. I am trying to communicate with the TCU that undergoes KWP2000 Protocol. I Have used the ADCS - KWP2000 functional palette. But i got stuck up initially in knowing the Mode, Source Address and the Target address (Transmit and Receive IDs) that are used as the input for vi. I got to know that the Target address is 0x03. But I do not know where to find the Source Address. kindly help me in finding the Source Address. Note that I use USB 8502 CAN Hardware Interface.

Thanks

[Hooovahh]

Crosspost and the advice there stands.  Make a new thread and read the documentation on your device.