VeriStand

cancel
Showing results for 
Search instead for 
Did you mean: 

Veristand and ECU MC Error -301075 with XCP over CAN seed key DLL

I am trying to get a simple veristand project utilizing the ECU MC toolkit to connect to an engine control module using XCP over CAN and a seed key dll pair per the XCP Seed/Key Master document on the NI website (https://decibel.ni.com/content/docs/DOC-21179). When I deploy to my realtime target (PXIe-8135 embedded controller and PXI-8513 CAN card in a PXIe-1071 chassis) I keep getting the error -301075:  <nierror code="-301075">
ECU Measurement and Calibration Toolkit:  (Hex 0xFFFB67ED) CCP/XCP error: Access locked. The specified slave device resource was not unlocked using the Seed/Key mechanism. Check availability of a valid SeedKey DLL.

 

I don't know how to resolve this error. It appears it is not locating the rskXcp.dll file that NI provides which is on the RT target at /ni-rt/system. ecumc.ini is deployed to the same location. What is the root issue here? Does rskXcp.dll need to be in a different location? 

0 Kudos
Message 1 of 6
(6,560 Views)

Support for the XCP CCP Custom Device is handled on a specific thread.  If you post on this thread the people directly supporting the Custom Device at NI will be able to help you

 

http://forums.ni.com/t5/NI-VeriStand/XCP-and-CCP-Master-Add-On-for-NI-VeriStand-feedback/m-p/1123948

Regards,

Eric L.
Applications Engineering Specialist
National Instruments
0 Kudos
Message 2 of 6
(6,531 Views)
That is not true. That thread is locked and closed and was used before this custom device was an NI product. Please continue to use this thread or phone or email support.
Stephen B
0 Kudos
Message 3 of 6
(6,527 Views)

I've done some more research and found that there is currently a known issue with the ECU Toolkit that causes this error.  It prevents valid SeedKey Dlls from being read properly.  What version of VeriStand and the ECU toolkit are you using?

Regards,

Eric L.
Applications Engineering Specialist
National Instruments
0 Kudos
Message 4 of 6
(6,496 Views)

I am using the ECU toolkit V2.3.1 and also Veristand 2012

0 Kudos
Message 5 of 6
(6,480 Views)

Imay have been hasty declaring this a bug, I have some more information and ti seems like your SeedKey DLL is simply not configured correctly.  Is your seed key DLL compiled for RT? If not you'll need to use a remote seedkey server. We provide one as an example.

 

seedkeysrv.PNG

 

 

Also, the seedkey DLL attached to that post will only work for our example software ECU, not any actual ECU. Your ECU manufacturer will have to provide a seedkey DLL in order to communicate with the ECU. Refer to page 4-19 to 4-25 of the ECUMC manual for more information about using seedkeys.  

Regards,

Eric L.
Applications Engineering Specialist
National Instruments
0 Kudos
Message 6 of 6
(6,445 Views)