XCP and CCP Master Add-On for NI VeriStand feedback.

[PRK]

I have  xcp_ccp_nivs2010_v14.6_.zip devices installed at appropriate places. The RT driver vi from this refuses to open in labview 2010, though the driver for vx works is opening. 

[StephenB]

that is expected, I strip the front panels out to make the file sizes smaller.

To be honest I'm not sure what the issue could be other than an installation problem. My only advise is to double check the install. If that doesn't work I would contact our support engineers at www.ni.com/support

if they get stuck with this, I will work with them when I'm back in office next week (I'm currently out)

[bensnyder]

I've got a bench running VS2010 with ECUMC 2.02 (including the VS support) talking to a VX1100.  The sys def deploys fine and I can see System Time updating.  At first, I am not seeing measurements update until the system time reaches around 70 seconds and I get an error on the RT console:

******XCP and CCP Master CUSTOM DEVICE ERROR******                             
Source:    DAQ                                                                 
Code:    -301058                                 

After seeing this error, the measurements immediately begin to update.  Any ideas?

[h_yong]

Hello,

I am just starting to use the XCP add on and have some basic questions. Please let me know if this should be a separate thread or support ticket instead. I quickly skimmed through the previous pages and didn't see anyone with the same problems.

I am using VeriStand 2009 and so my XCP add on version is 12. My ECU Measurement and Calibration Toolkit is 2.1.6. Are these compatible? When I installed 2.1.6 to the RT target, it automatically selected a lot of other packages which I could not install because they were dependent on packages that I did not have, so I installed only 2.1.6.

The problem I have at this time is that from the VeriStand workspace I see the signals as described in the A2L file, but when I click OK after selecting a signal, my measurement or characteristic tool is grayed out as "Not Available." For teh Target IP Address, I should indicate the IP address of the target, correct? And with default port 55555?

On the realtime machine, I see in the XCP_CCP_Master_Error_Log error # -1074384742 on MC ECU Connect.vi everytime I toggle the Connect command.

Thanks in adavnce.

[StephenB · Accepted solution]

Ben,

It appears the custom device is failing to connect to the VX1100 the first time, then timing out (there is a 60 second timeout) and reestablishing connection. This obviously shouldn't be happening as we tested this extensively a while back when you shipped your VX1100 to us.

I suggest directly cotacting R&D for assistance. Perhaps they can replicate your setup again.

If anyone using ECUMC 2.2 encounters a problem with this add on, please contact R&D directly at canpse@ni.com

If you're not using ECUMC 2.2 and instead using a previous version, I encourage you to upgrade, but if you cannot... then I will continue to support you through this forum.

[StephenB]

Hyog,

I'm not sure where you got ECUMC 2.1.6... it isn't posted on the website anywhere and I was unaware that version existed. Do you mean 2.1.5?

Are you using PXI or cRIO?

When you install ECUMC to an RT target, you shouldn't have any problems with dependencies. Can you show me a screen shot or some more detail about what you're talking about?

Yes, you should put in the IP address of the RT target and the default port 55555 (unless you changed that port on the custom device's main page).

The error you're receiving is:

Possible reason(s):

NI-XNET:  (Hex 0xBFF6309A) The interface has already been opened with different cluster settings than the ones specified for this session. Solution: make sure that the cluster settings agree for the interface, or use a different interface.

This indicates to me that you have other XNET can traffic on the same port you're trying to use with XCP/CCP. Unfortunatley, at this time, ECUMC toolkit cannot open a port that is already in use by another session. This is something we are investigating for the future, but until then... you will have to use a seperate port for CCP/XCP.

[h_yong]

StephenB, thanks for your reply. I'm sorry that I mistyped the toolkit version. It is indeed 2.1.5. I do have the XNET custom device running within VeriStand, so I changed the port that the XCP add-on uses to 55550 (in the custom device in the system definition). However, I get the same error code when trying to connect. Do you have any other suggestions on why this might be? Thanks.

As for dependencies, I think I'm OK. Asking to install the ECU toolkit automatically adds a lot of other packages, but I was able to deselect those and install the ECU toolkit after manual deselection.

[StephenB]

When I said port, I meant the CAN port. Sorry. The way the communication works is this

Host <-----(TCP)-----> RT Target <-------(XCP/CCP)-----> ECU

So the host (workspace, api, etc) talks to the RT target over TCP, and when you change the port the XCP device is using... this is the communication path you're altering. It has nothing to do with the actual XCP/CCP communication to/from the ECU... just the communication between the host and the target. If you're not running more than 1 XCP/CCP custom device, you can usually just leave it at the default 55555 unless you have some specific IT or firewall issue.

What I think the error you're getting means is that you're telling the RT target to use a CAN port that is already in use by something else in your system definition. For example you might have an XNET port under hardware using CAN1, and you're also trying to use CAN1 with the XCP/CCP custom device. This won't work for reasons stated previously.

[h_yong]

Great, thanks for the explanation. Installing another XNET card an using another CAN port from there resolved this error. I will probably have more questions as I continue down the XCP path though. Thanks again.

[h_yong]

Hi Stephen B,

My colleague mentioned to me that he thinks XNET 1.4 allows opening a standard XNET CAN and an XCP session on one physical CAN port. Can you please confirm that is the case? Should I be able to run the XCP/CCP add-on for 2009 still after I upgrade to XNET 1.4?

Thanks.