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

[Lucabeer]

Ok, next week we should be able to have a run with it.

In the meanwhile, thank you very much!

[Lucabeer]

We tried the new version and it works like a charm!

Thank you very much!

[StephenB]

Fantastic! Thanks for the feedback.

[Joe_ctrls]

I ran into the following issues when testing the XCP and CCP Custom Device. When I try to pull specific CAN messages into the workspace the indicators remain red, which seems to indicate that it doesn't’find the channel. I also pulled out the diagnostic channels of the Custom Device and I get the following errors: Status = 0, Error Code = -301007.0

[StephenB]

Joe,

The explanation for that error is as follows:

"ECU Measurement and Calibration Toolkit:  (Hex 0xFFFB6831) The communication parameters for the ECU are not properly initialized. The parameters are probably not defined in the database file. Solution: Set the communication parameters for the ECU using mcSetProperty before connecting to the ECU."

Can you send a screenshot of the main page of the custom device? I'm specifically interested in the communication properties settings. It appears the A2L doesn't have all the settings properly set. Can you also attach the A2L file?

Thanks,

[StephenB]

If users of this add on have issues with the RT system crashing or unexpected behavior including error -301003, there is a possible fix by following these steps.

1. Navigate to "<Program Files>\National Instruments\RT Images\ECU Measurement and Calibration Toolkit\2.1.5.3.1"
2. Open "A2LReaderConfig.a2l" in a text editor
3. Scroll to the line that reads "MINIMIZE_FOOTPRINT   1   // This flag controls the memory footprint when reading in A2L files."
4. Change that line's value to 0, reading "MINIMIZE_FOOTPRINT   0   // This flag controls the memory footprint when reading in A2L files."
5. Save and close
6. Open Measurement and Automation Explorer
7. Locate your RT PXI target under remote systems
8. Expand the target and right click software -> add/remove programs
9. Locate the ECU Measurement and Calibration Toolkit and click the glyph, then select reinstall

This issue will be fixed in a future version of ECUMC toolkit.

[StephenB]

The XCP and CCP Master Add-On for NI VeriStand has graduated to a shipping feature with the latest release of the NI ECU Measurement and Calibration Toolkit (version 2.2).  The version on this page will continue to work but all future support and feature improvements by National Instruments will be managed through the new ECU Measurement and Calibration Toolkit release.

If you are an existing XCP and CCP Master Add-on user and have purchased a copy of the NI ECU Measurement and Calibration Toolkit, the upgrade to the new version is free and can be ordered from NI using part number 850349J-03.  To order, simply call 1-800-531-5066 and ask for your free upgrade using part number 850349J-03.

[bensnyder]

On one of our first benches that we put VeriStand on, we recently updated from VS2009 to VS2010 and have struggled to get the XCP communication back up and running.  This is with the VX1100 setup.  I updated the ECUMC toolkit to 2.2.0fi and I installed XCP CD v14.6.  I can deploy from windows just fine, however, when I deploy to an RT target I get:

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
The VeriStand Gateway encountered an error while deploying the System Definition file.

Details:
Error 1003 occurred at Project Window.lvlib:Project Window.vi >> NI_VS Workspace ExecutionAPI.lvlib:NI VeriStand - Connect to System.vi

Possible reason(s):

LabVIEW:  The VI is not executable. Most likely the VI is broken or one of its subVIs cannot be located. Select File>>Open to open the VI and then verify that you are able to run it.
=========================
NI VeriStand:  Open VI Reference in Custom Devices Storage.lvlib:Open Device Reference (HW Interface).vi->Custom Devices Storage.lvlib:Initialize Device (HW Interface).vi->NI VeriStand Engine.lvlib:Initialize Inline Custom Devices.vi->NI VeriStand Engine.lvlib:VeriStand Engine State Machine.vi->NI VeriStand Engine.lvlib:VeriStand Engine.vi->NI VeriStand Engine.lvlib:VeriStand Engine Wrapper (RT).vi<APPEND>
VI Path: c:\ni-rt\NIVeriStand2010\Custom Devices\XCP and CCP Master\XCP and CCP Master RT Driver VI.vi

* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *

Any ideas?

[StephenB]

Ben,

ECUMC 2.2 includes support for NI VeriStand 2010 and 2011 so when you install it... There is an option to install the custom device (version 15.1).

Version 14.6 of the custom device is not compatible with ECUMC 2.2 and if you need to use 14.6 for legacy reasons then it must be used with ECUMC 2.1.5 http://joule.ni.com/nidu/cds/view/p/id/2259/lang/en

To fix your situation you must uninstall ECUMC 2.2 and either reinstall it to get version 15.1 of the add-on or install ECUMC 2.1.5 and version 14.6 of the add-on.

[StephenB]

Oh and after reinstalling on windows you will need to reinstall on the RT target