XCP CCP Custom Device Communication errors

[AldhairGarza]

If i want to test it on another PC with Veristand 2015, i must remove all the drivers for 2016 from the PXI and install the ones for 2015, right?

[JefeL]

Correct. I typically format the RT target when installing a fresh software stack to ensure I am working with a clean slate.

[AldhairGarza]

Ok now i'm working directly with the Slave and the labels in the Veristand Workspace are no longer red but blue and i get some readings that I don't know if they are right yet.

But when I try to modify a Characteristic I get the error -301073 Access Denied.

I read this post XCP ECU M&C Toolkit: error -301073 and my a2l file doesn't require apparently a Seedkey Dll File.

 Any Idea of what could be wrong?

[AldhairGarza]

[Edit] : From what I know the values that are read are wrong.

And if I add some anotherss Measurements I get the following error:

Possible Reasons: Memory structure or data structure is incorrect.

Any Idea would be helpful, thanks.

[JefeL]

The "Access Denied" error is returned directly from the ECU and propagated straight up to the user. It indicates that either the ECU does require a seedkey or that the ECU does not support that functionality.

The A2L file is not required to contain the seedkey DLL name but it can. If you find out that the ECU does require a seedkey DLL and obtain one from the manufacturer, you can either add the name to the A2L file or override the empty value in the file through the custom device interface.

[AldhairGarza]

What do you mean by "It indicates that either the ECU does require a seedkey or that the ECU does not support that functionality."

Which functionality? What can I do if I know that it works well without a Seedkey file?

---

@JefeL

[JefeL]

Some ECUs don't require a seedkey DLL for measurement access but do require one for characteristic writes. The ECU will differentiate between measurements and characteristics which are different functionalities.

Do you know if the ECU provides differing levels of access? Does the ECU allow characteristic writes without a seedkey?

[AldhairGarza]

Yes apparently it works fine with another software (not Veristand) without a seedkey.

I think not, i think there are no different levels of access.

I don't know what else to do I tried everything I found on Internet.

[JefeL]

I think the next step is to enable CCP/XCP Logging on the miscellaneous tab. This will generate a log file of the exact CCP/XCP commands being transmitted and received to the ECU. The log file will be stored on the remote target and will be named XCP or CCP Master_Protocol_Log.txt. If you open it up in a text editor it will look something like the picture below but be much longer....

If confidentiality is a

We can FTP the log file over from the target and post it here. If confidentiality is a concern you can send it to me via private message. The log will tell us exactly what the exchange is between the ECU and the toolkit and give us a better idea of why the ECU is saying it is locked.

[AldhairGarza]

Ok we found the main problem. It was >>this<< "adapter" apparently it is not just an adapter but also a converter.

I edited the Edit a Parameter.VI  in order to read and write a Characteristic and also read Measurements.

I got the "Acces Denied" Error again and the XCP Set Cal Page.vi solved that

I picked some random Characteristics and Measurements from my A2L File and every works well in LabVIEW. I can read and write all the Characteristics I picked and the Measurements apparently work too.

I restarted the ECU and tried with the Veristand XCP or CCP Master Custom Device, the communication with the ECU is successful too, nevertheless I got the "Acces Denied" Error. Which I can solve by first running the VI from above ( Edit a Parameter.VI).

Once that I solved I deploy the Veristand Project and I got the following results. Some Characteristics/Measurements don't work (randomly).

I deployed the project 4 times in a row without changing any configuration.

I got the error :Error 74 occurred at String deserialisieren in XCPCCP Add-On Execution API.lvlib:Get Item Type Names.vi->Check Link Validity on Server.vi->XCP and CCP - Single Characteristic.vi:6900003 

Everything works but the red ones.

The difference with LabVIEW is that I do one Characteristic at the time.

So I tried using only one control in Veristand and change the Characteristic to read and I still got the Error 74 but It worked anyway.

My question is:

Is there any way to do in Veristand what this "XCP Set Cal Page.vi" does in LabVIEW?

Is there any explanation of why this Error 74 happens in Veristand?

Thank you again.

Regards