01-29-2013 03:04 PM
FYI: The ECUMC installer does indeed specifically have a NI VeriStand option in the list of supported "programming language" targets. It will be selected to install by default assuming NI VeriStand is already installed on the system.
01-29-2013 03:05 PM
Yes, thanks. I uninstalled and reinstalled with that option selected and will try at a later date to see if it works.
01-31-2013 08:05 PM
Hi hyog,
Have you managed to solve the problem?
I installed ECUMC 2.2.1 over VS2011SP1, and got problem right away.
I never installed any ECUMC custom device before.
Regards, Kate
01-31-2013 10:26 PM
Hi KateB,
The reinstall of ECU 2.2.1 seemed to have worked for me. It no longer throws an error upon VeriStand deployment to the RT target. I do get an error when I try to read or write values, but I think that's something on my end.
02-01-2013 03:39 AM
Hi hyog,
So sad...mine doesn't work so far...
02-19-2013 10:30 AM
Our ECU supports CCP and can be flashed using CCP.
Does this Add-On support that?
Thanks,
Craig
02-19-2013 11:12 AM
That is a good question that unfortunately has at least two answers. In theory ECU flashing through CCP will work with this Add-on assuming we are simply talking about communicating values over CCP channels defined by the A2L file. However, for the sake of ECU security, there is often a handshaking process including security logic (code) that occurs to unlock the ECU for programming. That's probably a good thing so someone is not able to freely reprogram your ECU. So I would expect there needs to be some customization of this XCP/CCP Master Add-on to accomplish this task. NI has done this customization for customers in the past via our Engineering Services group so you may contact your local NI Sales Engineer to start this process if you are interested in discussing further. Feel free to refer to this post.
Best regards,
John
02-20-2013 04:01 AM
Thanks John,
I think my next port of call is the ECU supplier.
02-25-2013 03:01 PM
hi stephan
We work with NIVS 2011 and Custom Device CAN CCP we want to switch our ECU from ROM to RAM (changin the calibration page adress) this feature is not possible with the current Add-on
we have try to use a simple addon (CD) to do this but unfortunately the CCP Add-on go in error and disconnect the ECU: our switch from ROM to RAM is working but we lost the ECU connection :
there is any way to reconnect the ECU after veristand deployement ???
I know from the ECU M&C Toolkit 2.2 New features within the XCP/CCP Custom Device for NI VeriStand:
there is a feature that allow to auto reconnect the ECU again (if ERROR) (how we can Support to set the Delay before reconnect time. This time defines the time to wait after an CCP/XCP communication error before trying to connect to the ECU again.)
HOW WE CAN DO-IT ???
Thank you in advance for your efficent collaboration
02-25-2013 03:07 PM
Hi Phil,
Now that this add-on is a shipping NI product and now just a web download, for support on the XCP and CCP Master Add-on for NI VeriStand, you should use the normal NI support channels. Please create a service request at ni.com/support so the developers of the add-on can assist you and hear your feedback.
As far as the connect functionality, this was added in ECUMC 2.2.1 http://joule.ni.com/nidu/cds/view/p/id/3451/lang/en