Automotive and Embedded Networks
Going to Labview USB-8502 from Canalyzer
Solved!
You're using LabVIEW 64 bit, this only works with 32 bit since the Vector DLL provided is 32 bit only. To be fair I could make the packages only install in 32 bit but I forgot to check that box when building the package.
wrote:
The DBC file can be saved into an A2L file. Using the National Instruments ECU toolkit with the A2L file will allow for simple straight forward CAN communication.
Sorry but you are mistaken. A DBC and an A2L share some characteristics but are two completely different file formats, and beyond that contain different information. One cannot be converted to another.
A DBC (as discussed in part 5 of my blog) is a file that basically defines how to get from a stream of bytes, to signals that are in engineering units, things like Volts, or Degrees C. This is basically a decoder for the data that in most cases is sent periodically (but can be event driven). For example if data is seen where the ID is 0x5 then the first byte needs to be multiplied by 0.1 and now it is in Degrees C. This is the kind of information in a DBC.
An A2L file is used for diagnostic communication. Very event driven communication, where all data sent will be on one ID and all data received will be on another. It has provisions for things like how to read and write parameters, characteristics and variables internal to the ECU. Things that if sent periodically would flood the bus with data. Imagine being able to adjust the timing of engine firing order for example.
Here is a handy diagram from vector.
If you do have an A2L then you can use NI's ECU Measurement and Calibration Toolkit to talk via the XCP/CCP protocol. Otherwise a DBC can be used in XNet.
@Korpz wrote:
Ahhh, Thank you. That did it!
Everytime I install a program that is 64 bit, I regret it. I reinstalled the 32 bit version and it worked great. Thanks again!
This is definitely a major flaw in LabVIEW. In all other software packages I can think of, if a 64 bit and 32 bit versions are offered, and your system is 64 bit, why would you ever choose the 32 bit? Downloading a a virtual machine software? Get 64 bit. Downloading VLC? 64 bit. 7-Zip? Office Suite? etc. When it comes to LabVIEW not all toolkits are 64 bit, and some will never be due to dependencies. Then there is the complication with DLLs as you've found. Just another reason pure G is prefered when possible I guess.
EDIT: Oh and apparently it maybe possible to convert from a DBC to an A2L using some Vector software, but only if the ECU and diagnostic information needed for XCP is embedded in the DBC. This depends on where the DBC originates from, and what content is inside it.
Not sure where you are in the world, but I'm fortunate enough to have an NI office relatively close to me. On several occasions I've called them up and ask about a loner and they are very accommodating assuming they actually have the hardware on hand. There were a few times where we had the wrong cable and were able to borrow the right one until the correct one could be purchased. There's also been times when we wanted to prototype with some hardware first and they helped us out.
