XCP connection problem

[prithviKp]

Hello everybody,

I have a very similar problem as mentioned in the link below:

http://forums.ni.com/ni/board/message?board.id=30&message.id=3202&query.id=250743#M3202 

Since i dont see any solution to the above problem i shall put forth the exact nature of my problem. 

But i shall put forth the exact nature of my problem. 

I am using the USB-8473 device (for XCP communication) .I am using ECU and Calibration tool kit.  I am using the VIs given by the ECU and calibration tool kit.

Following is the procedure used to connect to the device:

1. The first Vi used is the MC ECU Open. Here there is no error. (I am using CAN0)

2. The second VI is the MC ECU connect. This VI always times out and says it is not able to connect to the slave device.

When I close these Vis and open MAX and check the Bus Monitor, I am able to see lots of messages on the BUS. This same USB device is being used on other computers and it is working well. In all the other computers also the CAN0 is the interface name given.

Please let me know how to resolve this problem.

Thanks in advance.

Prithvi. 

[Vincent_Gh]

I have kind of the same problem as yours. Any solving meanwhile?

Best,

Vincent

[prithviKp]

Hi Vincent,

This problem seems to be one those unsolved NI problems. Still working on it. I will post the solution in case i find one 🙂 

[O_Proulx]

Hello Prithvi,

There could be a number of things happening with the ECU Connect VI. First off, can you verify that your A2L is using the proper baudrate.  You can look at the A2L manually, or you can use the MC Get Property VI to do so.  Are you using a seedkey.dll for this? Are you using "XCP:CAN0" for interface name? 

If all this is correct, do you have another CAN port available to get a bus capture while your application is running?  You can use the bus monitor to save the log to disk and you could post it here.  

Have a great day.

[prithviKp]

Found the solution 🙂

As Proulx mentioned i checked all the parameters and they all seemed to be OK. But ECU MC connect was not functioning properly.

We have two systems in which ECU MC connect VI was functioning properly. We started examining the differences between the system in which the VI was not functioning and the systems in which it was working properly. We use Labview 8.6. The only difference between the systems was the version of ECU MC toolkit version. In the system in which XCP was working correctly the version used was 2.1.2 and in the system in which the XCP was not  functioning properly the version used was 2.1.0.

Actually while installing 2.1.0, it never showed Labview 8.6. My understanding is that 2.1.0 does not support Labview 8.6. This we noticed later. While installing 2.1.2 it also showed Labview 8.6. Once we installed ECU MC toolkit 2.1.2 ECU MC connect VI is functioning properly.

Conclusions (from my understanding) : Check if your ECU MC toolkit supports the Labview version you are using. I would recommend to use ECU MC toolkit 2.1.2 if you are using Labview 8.6.

Please throw more light on this if there is something more to be added or correct me if am wrong.

But my tool kit is working now 🙂

-Thanks 

Prithvi. 

[Vincent_Gh]

Glad to hear you managed it!

I also did. In my case the parameters were set incorrect and also, I had some inconsistency with a2l file.

Best regards,

Vincent